Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c042813f3c828ef601b82cafc8dc18a156bb6b28700c41fc19357c7dd101b71

Tx prefix hash: 2438f071fab53e298eed9f545871c20ee7bd076e9549d99a8d54c4b962abeba3
Tx public key: 219b9d5e4103f3337e5206e9d17fe74b3a428614a26605af4ec19be85e9d592b
Timestamp: 1711082934 Timestamp [UCT]: 2024-03-22 04:48:54 Age [y:d:h:m:s]: 00:358:11:04:30
Block: 983644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256296 RingCT/type: yes/0
Extra: 01219b9d5e4103f3337e5206e9d17fe74b3a428614a26605af4ec19be85e9d592b02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7281c1fe7cce1f1006acda7b8f09a0a109e7a253e50f4aac3dc719d9dafb4c82 0.600000000000 1443785 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": 983654, "vin": [ { "gen": { "height": 983644 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7281c1fe7cce1f1006acda7b8f09a0a109e7a253e50f4aac3dc719d9dafb4c82" } } ], "extra": [ 1, 33, 155, 157, 94, 65, 3, 243, 51, 126, 82, 6, 233, 209, 127, 231, 75, 58, 66, 134, 20, 162, 102, 5, 175, 78, 193, 155, 232, 94, 157, 89, 43, 2, 17, 0, 0, 0, 1, 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