Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df89f1f8be26a59a117b10c74dfd321f7c8d246dfa20e96e1cfdcbaf7cf7914f

Tx prefix hash: ae160e100906301108d02d659abbb81587615220b0a81377bffd5c4f1155829b
Tx public key: e37fa3ed84f68cdc18483daa101a132d2550217b754a5a09ac293a7c575abfad
Timestamp: 1700965054 Timestamp [UCT]: 2023-11-26 02:17:34 Age [y:d:h:m:s]: 01:047:03:38:19
Block: 899736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295097 RingCT/type: yes/0
Extra: 01e37fa3ed84f68cdc18483daa101a132d2550217b754a5a09ac293a7c575abfad02110000000233af99f4000000000000000000

1 output(s) for total of 0.640916006000 dcy

stealth address amount amount idx
00: 4be9b5c9d1f397c8cc1842729723adfae58cc9ee8406b06cf8e4cb65d39c8e8c 0.640916006000 1356199 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": 899746, "vin": [ { "gen": { "height": 899736 } } ], "vout": [ { "amount": 640916006, "target": { "key": "4be9b5c9d1f397c8cc1842729723adfae58cc9ee8406b06cf8e4cb65d39c8e8c" } } ], "extra": [ 1, 227, 127, 163, 237, 132, 246, 140, 220, 24, 72, 61, 170, 16, 26, 19, 45, 37, 80, 33, 123, 117, 74, 90, 9, 172, 41, 58, 124, 87, 90, 191, 173, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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