Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a66510e15960522019664b1e99fddf516e756a9b6092bfaa2a45e6d1d519b467

Tx prefix hash: eaf06cc1b255fec470a058390509adc432ff9621ffbd8c68dda7e9c26bff8e71
Tx public key: d4a6d94cba847ed3ec0aaf69c1e9a22afbd2d52774479532509ceeb9da3e2615
Timestamp: 1701607162 Timestamp [UCT]: 2023-12-03 12:39:22 Age [y:d:h:m:s]: 01:338:09:30:22
Block: 905065 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 500705 RingCT/type: yes/0
Extra: 01d4a6d94cba847ed3ec0aaf69c1e9a22afbd2d52774479532509ceeb9da3e261502110000000875e3f0e9000000000000000000

1 output(s) for total of 0.615380770000 dcy

stealth address amount amount idx
00: 0a2477ff543c0dd00718e0c5b055bec62ac00f0bb55e9ea247bb32e2e8b92069 0.615380770000 1361930 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": 905075, "vin": [ { "gen": { "height": 905065 } } ], "vout": [ { "amount": 615380770, "target": { "key": "0a2477ff543c0dd00718e0c5b055bec62ac00f0bb55e9ea247bb32e2e8b92069" } } ], "extra": [ 1, 212, 166, 217, 76, 186, 132, 126, 211, 236, 10, 175, 105, 193, 233, 162, 42, 251, 210, 213, 39, 116, 71, 149, 50, 80, 156, 238, 185, 218, 62, 38, 21, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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