Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae19ffdc9cca4c2a66f8c20f44983e987669fb66b071132cf204f660cc6e6eb6

Tx prefix hash: 78ccaa31f9bffb464c07d0f1c3571497b1ce29c41938477b3b1ad5da9329bf58
Tx public key: 130703fb3c96b4de9d382629274c88fd0bc85b6afeb879f5ce5a61d77b88aa87
Timestamp: 1735766781 Timestamp [UCT]: 2025-01-01 21:26:21 Age [y:d:h:m:s]: 00:169:03:53:14
Block: 1188133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120595 RingCT/type: yes/0
Extra: 01130703fb3c96b4de9d382629274c88fd0bc85b6afeb879f5ce5a61d77b88aa87021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0217c470ef75c30e82446411de8d11d8bc755edddbb6c56d8e92446f9e6ddfa9 0.600000000000 1674634 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": 1188143, "vin": [ { "gen": { "height": 1188133 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0217c470ef75c30e82446411de8d11d8bc755edddbb6c56d8e92446f9e6ddfa9" } } ], "extra": [ 1, 19, 7, 3, 251, 60, 150, 180, 222, 157, 56, 38, 41, 39, 76, 136, 253, 11, 200, 91, 106, 254, 184, 121, 245, 206, 90, 97, 215, 123, 136, 170, 135, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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