Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5bf0c9ff88fe98e06bc9ea0d8437da1d7d0391bc8f0f98783798eadf67a61ba7

Tx prefix hash: 68134510019359938a3efcec2269034e6b42058f482482fafb43e55dc0d9fbf0
Tx public key: c7310e3f45ec7d13ad33ceef1df2b668da76fb9787d1988ce85118093a64e4ec
Timestamp: 1735098112 Timestamp [UCT]: 2024-12-25 03:41:52 Age [y:d:h:m:s]: 00:100:07:08:17
Block: 1182612 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71463 RingCT/type: yes/0
Extra: 01c7310e3f45ec7d13ad33ceef1df2b668da76fb9787d1988ce85118093a64e4ec0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90a441f84ad991d75c756f32d9d1a987b95780cb7c8fdd4997affa6e17d6e1e8 0.600000000000 1669047 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": 1182622, "vin": [ { "gen": { "height": 1182612 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90a441f84ad991d75c756f32d9d1a987b95780cb7c8fdd4997affa6e17d6e1e8" } } ], "extra": [ 1, 199, 49, 14, 63, 69, 236, 125, 19, 173, 51, 206, 239, 29, 242, 182, 104, 218, 118, 251, 151, 135, 209, 152, 140, 232, 81, 24, 9, 58, 100, 228, 236, 2, 17, 0, 0, 0, 2, 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