Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8666c2ef04fd7973fa53ace6eb9e9d08c1ab9bc5f14f0e66f38efe014b33c2b7

Tx prefix hash: 2ff2d0b793d15772ab23f6720bc4cfc81687d622952a86496f7ee1601b261959
Tx public key: f100be3b4e09c4a07ec53c55f1f4a715ea00904160fad927a262b7ac9943d166
Timestamp: 1577183211 Timestamp [UCT]: 2019-12-24 10:26:51 Age [y:d:h:m:s]: 04:318:00:33:03
Block: 30596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1116446 RingCT/type: yes/0
Extra: 01f100be3b4e09c4a07ec53c55f1f4a715ea00904160fad927a262b7ac9943d1660211000000dce39b962a000000000000000000

1 output(s) for total of 485.985836473000 dcy

stealth address amount amount idx
00: 09f18bcc2e29305ae0299a2dcfa1b3ddb552bb9e1b6a1931a3df7ea22c45cfaa 485.985836473000 50520 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": 30606, "vin": [ { "gen": { "height": 30596 } } ], "vout": [ { "amount": 485985836473, "target": { "key": "09f18bcc2e29305ae0299a2dcfa1b3ddb552bb9e1b6a1931a3df7ea22c45cfaa" } } ], "extra": [ 1, 241, 0, 190, 59, 78, 9, 196, 160, 126, 197, 60, 85, 241, 244, 167, 21, 234, 0, 144, 65, 96, 250, 217, 39, 162, 98, 183, 172, 153, 67, 209, 102, 2, 17, 0, 0, 0, 220, 227, 155, 150, 42, 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