Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 468b5761690568ea07c3a02449f1079dab9bfba106afd066951c27b07008a1cc

Tx prefix hash: f45849ea43f758aa69a8392a47b4fb5f24c39596256f3a2bf67bec919a0c6e6f
Tx public key: 1678cda63e9fe3c694217d86d70f102cdd9fc044d85450d633ccc1b8b1e0a743
Timestamp: 1716988793 Timestamp [UCT]: 2024-05-29 13:19:53 Age [y:d:h:m:s]: 00:316:08:15:25
Block: 1032603 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226082 RingCT/type: yes/0
Extra: 011678cda63e9fe3c694217d86d70f102cdd9fc044d85450d633ccc1b8b1e0a74302110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e52c8a63b799ab1b8f98eda24ec88279df4dae0a1272b3d38a0c13f593ec6dc0 0.600000000000 1501056 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": 1032613, "vin": [ { "gen": { "height": 1032603 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e52c8a63b799ab1b8f98eda24ec88279df4dae0a1272b3d38a0c13f593ec6dc0" } } ], "extra": [ 1, 22, 120, 205, 166, 62, 159, 227, 198, 148, 33, 125, 134, 215, 15, 16, 44, 221, 159, 192, 68, 216, 84, 80, 214, 51, 204, 193, 184, 177, 224, 167, 67, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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