Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7289891bfa2e7f5e8681f0f5989306be4b4a46dd7c730e19f427c8b7d62dc2cf

Tx prefix hash: 5b49034913b03df2209e8757068668142e74992e62c7cc6b62c1fc928af5bf5d
Tx public key: 98244a07ff8f53bf7c10f8b7942b4457ddcda340d7c3b2253fd279647d428b1c
Timestamp: 1737486050 Timestamp [UCT]: 2025-01-21 19:00:50 Age [y:d:h:m:s]: 00:335:22:45:43
Block: 1202322 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237698 RingCT/type: yes/0
Extra: 0198244a07ff8f53bf7c10f8b7942b4457ddcda340d7c3b2253fd279647d428b1c021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef12cbe6a58db7e48687d767fe06b1e2854f2742cfbf62c6d6bc8bee7647eee1 0.600000000000 1688985 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": 1202332, "vin": [ { "gen": { "height": 1202322 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef12cbe6a58db7e48687d767fe06b1e2854f2742cfbf62c6d6bc8bee7647eee1" } } ], "extra": [ 1, 152, 36, 74, 7, 255, 143, 83, 191, 124, 16, 248, 183, 148, 43, 68, 87, 221, 205, 163, 64, 215, 195, 178, 37, 63, 210, 121, 100, 125, 66, 139, 28, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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