Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a11e6324bfb907b3fd50df05c9b99d100fbfb1562df22da4a31eb732e3f4946

Tx prefix hash: e775d51c194ebc7cc4dfb4d8258a961ea041576e9dc7006f897f6b7e8a7d0b9f
Tx public key: 93546d1e9bf3f84eefc5b68f03c47e1ad5eb47e19cfdcd6b15fe15b43653f0a2
Timestamp: 1737122699 Timestamp [UCT]: 2025-01-17 14:04:59 Age [y:d:h:m:s]: 00:058:21:12:00
Block: 1199358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41880 RingCT/type: yes/0
Extra: 0193546d1e9bf3f84eefc5b68f03c47e1ad5eb47e19cfdcd6b15fe15b43653f0a2021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e7140f394eb80e193cd9b29dd7d3bde01ae60f34c14754407894d8120781804 0.600000000000 1685989 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": 1199368, "vin": [ { "gen": { "height": 1199358 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e7140f394eb80e193cd9b29dd7d3bde01ae60f34c14754407894d8120781804" } } ], "extra": [ 1, 147, 84, 109, 30, 155, 243, 248, 78, 239, 197, 182, 143, 3, 196, 126, 26, 213, 235, 71, 225, 156, 253, 205, 107, 21, 254, 21, 180, 54, 83, 240, 162, 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