Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6770a614846dd1fbd18ca1fa3d58bc4342ab07b48406752f3db90a789c105538

Tx prefix hash: 6f235ec5e305fc5756d2fc553fb1e68a43d78425d57641382827a5eb3cd41799
Tx public key: 9a8a69fff9095a64e51fd9c841f76603134512e37d6ca1d4c789cc5d88fafab7
Timestamp: 1681003874 Timestamp [UCT]: 2023-04-09 01:31:14 Age [y:d:h:m:s]: 02:009:10:11:43
Block: 734559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 528838 RingCT/type: yes/0
Extra: 019a8a69fff9095a64e51fd9c841f76603134512e37d6ca1d4c789cc5d88fafab7021100000005b3164c24000000000000000000

1 output(s) for total of 2.259962999000 dcy

stealth address amount amount idx
00: 851f6df73a1fc1168b94dd5f210fc7d3d17bb769dd6730d2bee06569b0674e13 2.259962999000 1180784 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": 734569, "vin": [ { "gen": { "height": 734559 } } ], "vout": [ { "amount": 2259962999, "target": { "key": "851f6df73a1fc1168b94dd5f210fc7d3d17bb769dd6730d2bee06569b0674e13" } } ], "extra": [ 1, 154, 138, 105, 255, 249, 9, 90, 100, 229, 31, 217, 200, 65, 247, 102, 3, 19, 69, 18, 227, 125, 108, 161, 212, 199, 137, 204, 93, 136, 250, 250, 183, 2, 17, 0, 0, 0, 5, 179, 22, 76, 36, 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