Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99c2108d9e51e2309a00de0392085b3fb9dbd0a8479db94946f51103f4532a31

Tx prefix hash: 7c886e3faf79c9eeecef00c980df25f932bd6e31028fa6d6db5665a7fedc5c7e
Tx public key: a1190e0948b7c9d4a784e935998d856f975ab9f1713a713375101ecebce4aaba
Timestamp: 1725953474 Timestamp [UCT]: 2024-09-10 07:31:14 Age [y:d:h:m:s]: 00:213:04:39:22
Block: 1106914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152217 RingCT/type: yes/0
Extra: 01a1190e0948b7c9d4a784e935998d856f975ab9f1713a713375101ecebce4aaba02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1eae2b379d77d315c6575d0fad77d372ffbee7cc94f458b47f69ec788afadbe6 0.600000000000 1584517 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": 1106924, "vin": [ { "gen": { "height": 1106914 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1eae2b379d77d315c6575d0fad77d372ffbee7cc94f458b47f69ec788afadbe6" } } ], "extra": [ 1, 161, 25, 14, 9, 72, 183, 201, 212, 167, 132, 233, 53, 153, 141, 133, 111, 151, 90, 185, 241, 113, 58, 113, 51, 117, 16, 30, 206, 188, 228, 170, 186, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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