Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa28dfc8973452d54b01f15b2f81209def2087fd3e33b09ad0f7e957afaeb906

Tx prefix hash: ec6ac9dafe88e92a42c6bf5faefa72a621305b18f8de829ff04bd92091c27b1a
Tx public key: b701741d15fbab39edf6804857b7af8a9e363c4cb97e49943e6ff0775e2f9998
Timestamp: 1705509189 Timestamp [UCT]: 2024-01-17 16:33:09 Age [y:d:h:m:s]: 01:304:22:11:29
Block: 937402 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 476756 RingCT/type: yes/0
Extra: 01b701741d15fbab39edf6804857b7af8a9e363c4cb97e49943e6ff0775e2f999802110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a15332669c0f55b23814f4c9e42607e8b4dcc650f637072f69f7e17100827322 0.600000000000 1395456 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": 937412, "vin": [ { "gen": { "height": 937402 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a15332669c0f55b23814f4c9e42607e8b4dcc650f637072f69f7e17100827322" } } ], "extra": [ 1, 183, 1, 116, 29, 21, 251, 171, 57, 237, 246, 128, 72, 87, 183, 175, 138, 158, 54, 60, 76, 185, 126, 73, 148, 62, 111, 240, 119, 94, 47, 153, 152, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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