Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a72460fb7733b0ee45c1f277adbe0612b346b8b05bd2c97090f2543485debae

Tx prefix hash: 9086c8e456589b30f3742bd6688342173d4bf8844844b8fadaf375f05a4ebeb4
Tx public key: 37210887a9c1d735d5e568b55e0cc37a714fc882ef6e5f56300c1b08232c474a
Timestamp: 1696069718 Timestamp [UCT]: 2023-09-30 10:28:38 Age [y:d:h:m:s]: 01:200:19:18:15
Block: 859365 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 404572 RingCT/type: yes/0
Extra: 0137210887a9c1d735d5e568b55e0cc37a714fc882ef6e5f56300c1b08232c474a0211000000064b8f5122000000000000000000

1 output(s) for total of 0.872101550000 dcy

stealth address amount amount idx
00: e8adb2b09af89cce5d9198d79732a249e9e6b3f93acf34d150d1b045d4e3c431 0.872101550000 1313589 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": 859375, "vin": [ { "gen": { "height": 859365 } } ], "vout": [ { "amount": 872101550, "target": { "key": "e8adb2b09af89cce5d9198d79732a249e9e6b3f93acf34d150d1b045d4e3c431" } } ], "extra": [ 1, 55, 33, 8, 135, 169, 193, 215, 53, 213, 229, 104, 181, 94, 12, 195, 122, 113, 79, 200, 130, 239, 110, 95, 86, 48, 12, 27, 8, 35, 44, 71, 74, 2, 17, 0, 0, 0, 6, 75, 143, 81, 34, 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