Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2acb437098c566fc2eddc63e6b8573c009840c0ad5d17d0301c61ebbc5b0721

Tx prefix hash: ff2913f0d2f8ed804fc93e47276faca7fe23dc5e612a5bf8b25f614e056794c5
Tx public key: f1cf36f31172b98ceccd4d5851c01f77eb2329342a0f1fb14ba1f736292e367a
Timestamp: 1740813777 Timestamp [UCT]: 2025-03-01 07:22:57 Age [y:d:h:m:s]: 00:258:17:53:08
Block: 1229648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182677 RingCT/type: yes/0
Extra: 01f1cf36f31172b98ceccd4d5851c01f77eb2329342a0f1fb14ba1f736292e367a0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c57617283224e9067b3571f92c6e5abd8e50485e5cfc15403ccd1cd5bf38e2b 0.600000000000 1716535 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": 1229658, "vin": [ { "gen": { "height": 1229648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c57617283224e9067b3571f92c6e5abd8e50485e5cfc15403ccd1cd5bf38e2b" } } ], "extra": [ 1, 241, 207, 54, 243, 17, 114, 185, 140, 236, 205, 77, 88, 81, 192, 31, 119, 235, 35, 41, 52, 42, 15, 31, 177, 75, 161, 247, 54, 41, 46, 54, 122, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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