Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64c061708e1de16991ef6bb6f33293c43a40dad1a427dff22b867c7750980430

Tx prefix hash: 325e8649435ab44aaa0c72cd6f5521b4700fc6b59c9dcd886e6b1dc60fe3802f
Tx public key: e0f19cee0116e2f615732ba9e7aa8d3074e709aa34e060954f96bb9dc6cf4cba
Timestamp: 1734412086 Timestamp [UCT]: 2024-12-17 05:08:06 Age [y:d:h:m:s]: 00:327:14:31:14
Block: 1176947 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231636 RingCT/type: yes/0
Extra: 01e0f19cee0116e2f615732ba9e7aa8d3074e709aa34e060954f96bb9dc6cf4cba021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 680233bf4f75f10a718246498e8732265b65e4a0d96cce8c7df6755b15c68d88 0.600000000000 1663308 of 15

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": 1176957, "vin": [ { "gen": { "height": 1176947 } } ], "vout": [ { "amount": 600000000, "target": { "key": "680233bf4f75f10a718246498e8732265b65e4a0d96cce8c7df6755b15c68d88" } } ], "extra": [ 1, 224, 241, 156, 238, 1, 22, 226, 246, 21, 115, 43, 169, 231, 170, 141, 48, 116, 231, 9, 170, 52, 224, 96, 149, 79, 150, 187, 157, 198, 207, 76, 186, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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