Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7dd472493c64c0fb293460f4ade7ab2f73d7ae1a47c4885678a09061a7cacff

Tx prefix hash: 4dfc6ee7b3c561f0d005107a1802bdc602218cea2e59fb2e27d6082c3133f78d
Tx public key: 7643fa98d5b442350b57502be56a9b1c9da46b3e57a87c31a8032a78d8923853
Timestamp: 1576427387 Timestamp [UCT]: 2019-12-15 16:29:47 Age [y:d:h:m:s]: 05:134:06:56:35
Block: 27816 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1242372 RingCT/type: yes/0
Extra: 017643fa98d5b442350b57502be56a9b1c9da46b3e57a87c31a8032a78d89238530211000000159159db1e000000000000000000

1 output(s) for total of 496.403586400000 dcy

stealth address amount amount idx
00: 3dd957df5d90942a9070e5a4b2a7459f4fea92c58c56710e6c51b445dcf2e488 496.403586400000 45872 of 0

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": 27826, "vin": [ { "gen": { "height": 27816 } } ], "vout": [ { "amount": 496403586400, "target": { "key": "3dd957df5d90942a9070e5a4b2a7459f4fea92c58c56710e6c51b445dcf2e488" } } ], "extra": [ 1, 118, 67, 250, 152, 213, 180, 66, 53, 11, 87, 80, 43, 229, 106, 155, 28, 157, 164, 107, 62, 87, 168, 124, 49, 168, 3, 42, 120, 216, 146, 56, 83, 2, 17, 0, 0, 0, 21, 145, 89, 219, 30, 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