Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d29b28a4c511a2bc1ca38c0b180dc7c6db852b33b4817514d5c6f4dc6bda9ab

Tx prefix hash: 99f6c95b3fd6ee1bb9f9549bbd5c785a0e6a172aa2af3af0a4c26e4e1c1eb21d
Tx public key: 62be1c007c3338e8caaf9052664ca698782f9dfb15105800f683bad0376512e4
Timestamp: 1719442660 Timestamp [UCT]: 2024-06-26 22:57:40 Age [y:d:h:m:s]: 01:147:01:55:53
Block: 1052927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363668 RingCT/type: yes/0
Extra: 0162be1c007c3338e8caaf9052664ca698782f9dfb15105800f683bad0376512e402110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8997924a39092624e5ddaefb63b9283628a82c8c517f3c898512561f6030e069 0.600000000000 1523272 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": 1052937, "vin": [ { "gen": { "height": 1052927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8997924a39092624e5ddaefb63b9283628a82c8c517f3c898512561f6030e069" } } ], "extra": [ 1, 98, 190, 28, 0, 124, 51, 56, 232, 202, 175, 144, 82, 102, 76, 166, 152, 120, 47, 157, 251, 21, 16, 88, 0, 246, 131, 186, 208, 55, 101, 18, 228, 2, 17, 0, 0, 0, 2, 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