Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2e53f95c348249f3b9ffbb75d996a050f6d54d7a2f9b2a38b37307f1d2cd07b

Tx prefix hash: 7bba3c58ef933e46bb0dc36f163d53f2af6afb47704ef3d48dca25568f4e51fe
Tx public key: 606255dffb51b3139c85fcc6991fd40a8f10c635bf233c463ceaf31046f5139b
Timestamp: 1719662597 Timestamp [UCT]: 2024-06-29 12:03:17 Age [y:d:h:m:s]: 01:175:21:37:21
Block: 1054763 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384298 RingCT/type: yes/0
Extra: 01606255dffb51b3139c85fcc6991fd40a8f10c635bf233c463ceaf31046f5139b0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e6a64c6c320d00ee839f5d50412cb1cb16c2fc4eed0ff2b9287dead0cfe1a12 0.600000000000 1525148 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": 1054773, "vin": [ { "gen": { "height": 1054763 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e6a64c6c320d00ee839f5d50412cb1cb16c2fc4eed0ff2b9287dead0cfe1a12" } } ], "extra": [ 1, 96, 98, 85, 223, 251, 81, 179, 19, 156, 133, 252, 198, 153, 31, 212, 10, 143, 16, 198, 53, 191, 35, 60, 70, 60, 234, 243, 16, 70, 245, 19, 155, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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