Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88683f67ef508c52cedf24215f3648a5b709a2165d51c9219c31f537798f40ab

Tx prefix hash: 8a97f5223ee90c768fff36eb38181a3654de1d99e79a9bcae22903ab3697d1bb
Tx public key: 770c1e9b2f091f9b061eee823d2936212d67147518a3d09c2831ee2d695acb73
Timestamp: 1736569132 Timestamp [UCT]: 2025-01-11 04:18:52 Age [y:d:h:m:s]: 00:066:09:11:38
Block: 1194781 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47236 RingCT/type: yes/0
Extra: 01770c1e9b2f091f9b061eee823d2936212d67147518a3d09c2831ee2d695acb73021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04c8d70e1d05259a444a8a44ff7fbc4ff86889ef0ec2a9e987bdbcc5bf5d7e2a 0.600000000000 1681358 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": 1194791, "vin": [ { "gen": { "height": 1194781 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04c8d70e1d05259a444a8a44ff7fbc4ff86889ef0ec2a9e987bdbcc5bf5d7e2a" } } ], "extra": [ 1, 119, 12, 30, 155, 47, 9, 31, 155, 6, 30, 238, 130, 61, 41, 54, 33, 45, 103, 20, 117, 24, 163, 208, 156, 40, 49, 238, 45, 105, 90, 203, 115, 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