Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 358ea1f4717ca0f3d814da1777de8759e02a7b13c2f8824191fab6775eaf1832

Tx prefix hash: 4908ef3f6758fa69074a01d40b2c5dc6b6c407fcba0a1ef80a56b6bdfa8e28ae
Tx public key: 3db6309087e052d84169f179c6d8328bcb81bd8f315f3d68b0d6691879f3294e
Timestamp: 1719493076 Timestamp [UCT]: 2024-06-27 12:57:56 Age [y:d:h:m:s]: 00:352:23:02:39
Block: 1053341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252174 RingCT/type: yes/0
Extra: 013db6309087e052d84169f179c6d8328bcb81bd8f315f3d68b0d6691879f3294e02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5eae1ce2c5ebbbfc4d09934119f042422ad592861a217036e16147339954cb92 0.600000000000 1523688 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": 1053351, "vin": [ { "gen": { "height": 1053341 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5eae1ce2c5ebbbfc4d09934119f042422ad592861a217036e16147339954cb92" } } ], "extra": [ 1, 61, 182, 48, 144, 135, 224, 82, 216, 65, 105, 241, 121, 198, 216, 50, 139, 203, 129, 189, 143, 49, 95, 61, 104, 176, 214, 105, 24, 121, 243, 41, 78, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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