Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0621dbb7cca937a14bcb00a2857fdf27541e0ae2575b1adde1b3df6c23b3594

Tx prefix hash: 2e2200ba86c36734e0163c7b55fe0f298fff8bd8d8d366cb045426092b202d86
Tx public key: 06911e2922e6f7cb435a3f3988580098ec7b7fdcf0e0d24269ea8062243c0823
Timestamp: 1743357328 Timestamp [UCT]: 2025-03-30 17:55:28 Age [y:d:h:m:s]: 00:234:02:17:48
Block: 1250709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165042 RingCT/type: yes/0
Extra: 0106911e2922e6f7cb435a3f3988580098ec7b7fdcf0e0d24269ea8062243c08230211000000021a970403000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18966d409d79df269c22fc0031e83f7f8a615ae62d59ce357fc377497bd2d433 0.600000000000 1737760 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": 1250719, "vin": [ { "gen": { "height": 1250709 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18966d409d79df269c22fc0031e83f7f8a615ae62d59ce357fc377497bd2d433" } } ], "extra": [ 1, 6, 145, 30, 41, 34, 230, 247, 203, 67, 90, 63, 57, 136, 88, 0, 152, 236, 123, 127, 220, 240, 224, 210, 66, 105, 234, 128, 98, 36, 60, 8, 35, 2, 17, 0, 0, 0, 2, 26, 151, 4, 3, 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