Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c5d7dc2cf955949326eb3d4e82b63b6a98a5b65268f845f2ccd4ef6e5a6b7ae

Tx prefix hash: e9e53354d1da750a03b4529ef86d69f58d6a7b7ad1393f8db695b08400a16309
Tx public key: 6e03109c83c0db071b536f0d7a04b8f8728c9f20c4fb38007ad7cb28a66f2162
Timestamp: 1745604205 Timestamp [UCT]: 2025-04-25 18:03:25 Age [y:d:h:m:s]: 00:271:21:53:43
Block: 1269318 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191991 RingCT/type: yes/0
Extra: 016e03109c83c0db071b536f0d7a04b8f8728c9f20c4fb38007ad7cb28a66f21620211000000126c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7607b769f40d277576512438f23bd7f60b545664c2d73b036df2d0e9941ac706 0.600000000000 1756553 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": 1269328, "vin": [ { "gen": { "height": 1269318 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7607b769f40d277576512438f23bd7f60b545664c2d73b036df2d0e9941ac706" } } ], "extra": [ 1, 110, 3, 16, 156, 131, 192, 219, 7, 27, 83, 111, 13, 122, 4, 184, 248, 114, 140, 159, 32, 196, 251, 56, 0, 122, 215, 203, 40, 166, 111, 33, 98, 2, 17, 0, 0, 0, 18, 108, 152, 170, 61, 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