Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f796faadd9c32f37f90dc9a5613373c9a999c2f74cc4dbd4c1a9c57b82ba75e8

Tx prefix hash: aab62e3d5354d3d7eaedb43b39b99a4098ec17f5e52121cd65acced585daddbf
Tx public key: a19b12c359036e31e158a05be5f6e72a2c703c5fa8bc95931ad20b8e0bbbd255
Timestamp: 1722890740 Timestamp [UCT]: 2024-08-05 20:45:40 Age [y:d:h:m:s]: 00:170:08:22:13
Block: 1081522 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121824 RingCT/type: yes/0
Extra: 01a19b12c359036e31e158a05be5f6e72a2c703c5fa8bc95931ad20b8e0bbbd255021100000010e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2b1fd0b5f0c8f9e3a21ccf27b74ce557b07839ef58f618084ae8d3b3f42ad95 0.600000000000 1555299 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": 1081532, "vin": [ { "gen": { "height": 1081522 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2b1fd0b5f0c8f9e3a21ccf27b74ce557b07839ef58f618084ae8d3b3f42ad95" } } ], "extra": [ 1, 161, 155, 18, 195, 89, 3, 110, 49, 225, 88, 160, 91, 229, 246, 231, 42, 44, 112, 60, 95, 168, 188, 149, 147, 26, 210, 11, 142, 11, 187, 210, 85, 2, 17, 0, 0, 0, 16, 233, 20, 221, 21, 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