Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 56f4c00e8d2d02ce31cf8fece8cc7cf64d062f6bf2d98a114a92b850413c263e

Tx prefix hash: d4c036a7a021554a43678dbd779bd89847bfaa7bc286e88d025edabf89da7211
Tx public key: ccfccce520d1b17b54e5247aaa0c0aeeef0f9cc959a8bc7630da683114b3816e
Timestamp: 1700857334 Timestamp [UCT]: 2023-11-24 20:22:14 Age [y:d:h:m:s]: 01:172:06:04:27
Block: 898860 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384296 RingCT/type: yes/0
Extra: 01ccfccce520d1b17b54e5247aaa0c0aeeef0f9cc959a8bc7630da683114b3816e021100000003faf35c9c000000000000000000

1 output(s) for total of 0.645213834000 dcy

stealth address amount amount idx
00: 35455f540ed4c813c1d8462998441d45214fd9cf8fa56cf1e24b3db562c537c8 0.645213834000 1355297 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 898870, "vin": [ { "gen": { "height": 898860 } } ], "vout": [ { "amount": 645213834, "target": { "key": "35455f540ed4c813c1d8462998441d45214fd9cf8fa56cf1e24b3db562c537c8" } } ], "extra": [ 1, 204, 252, 204, 229, 32, 209, 177, 123, 84, 229, 36, 122, 170, 12, 10, 238, 239, 15, 156, 201, 89, 168, 188, 118, 48, 218, 104, 49, 20, 179, 129, 110, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8