Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12b2b533a0fe1f86518da5e012261389d9ca92974a3c68027ce763582381eee0

Tx prefix hash: c462c8729479119cc93c8cba1e9639cecf94c102929018d7de5db8b3c7d8f318
Tx public key: 6fa56196a6e7403f6e5cf5bc04b2d3959903345c47cad1cf61c60c631ea974e8
Timestamp: 1743938651 Timestamp [UCT]: 2025-04-06 11:24:11 Age [y:d:h:m:s]: 00:228:11:03:48
Block: 1255520 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161010 RingCT/type: yes/0
Extra: 016fa56196a6e7403f6e5cf5bc04b2d3959903345c47cad1cf61c60c631ea974e8021100000010dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34f1e8e4ca4d0b4e1d0ee01d0224cec575dd4827d300b22d5fb733ce87d92b85 0.600000000000 1742625 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": 1255530, "vin": [ { "gen": { "height": 1255520 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34f1e8e4ca4d0b4e1d0ee01d0224cec575dd4827d300b22d5fb733ce87d92b85" } } ], "extra": [ 1, 111, 165, 97, 150, 166, 231, 64, 63, 110, 92, 245, 188, 4, 178, 211, 149, 153, 3, 52, 92, 71, 202, 209, 207, 97, 198, 12, 99, 30, 169, 116, 232, 2, 17, 0, 0, 0, 16, 219, 181, 113, 193, 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