Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b1047b9d8488260420dfe5c9d1562826356f2f319d4ffa696a5d2ef7cc82127

Tx prefix hash: df11f92bee7ef7a8d42b5e35397bc94fab5978e1bc68c32f857c1165c10c28be
Tx public key: 34f73fdbbfa4f5e9e8122c147400c01c51516269dc7c7a606398644abc1bcafc
Timestamp: 1703092796 Timestamp [UCT]: 2023-12-20 17:19:56 Age [y:d:h:m:s]: 01:118:17:12:45
Block: 917406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345953 RingCT/type: yes/0
Extra: 0134f73fdbbfa4f5e9e8122c147400c01c51516269dc7c7a606398644abc1bcafc02110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3cb912b1a6326ec2498a3144a4c938359be209ff873c51c6f36d8c969f02d66 0.600000000000 1374980 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": 917416, "vin": [ { "gen": { "height": 917406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3cb912b1a6326ec2498a3144a4c938359be209ff873c51c6f36d8c969f02d66" } } ], "extra": [ 1, 52, 247, 63, 219, 191, 164, 245, 233, 232, 18, 44, 20, 116, 0, 192, 28, 81, 81, 98, 105, 220, 124, 122, 96, 99, 152, 100, 74, 188, 27, 202, 252, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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