Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5acf44898e1ce84419adc801cb1e9c11fec4a5dc9107c824ad2e09fd21aff785

Tx prefix hash: 7e2c1a4f62f1041174b03ed3f2878a896e54977273100e8aaa242976c9371cf7
Tx public key: 52b7d2b77543a77ea0fd6a74e3e56bea6ef5c4ec0b5ec6cc735dcc98c1d27a31
Timestamp: 1726416434 Timestamp [UCT]: 2024-09-15 16:07:14 Age [y:d:h:m:s]: 00:197:17:25:54
Block: 1110754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141128 RingCT/type: yes/0
Extra: 0152b7d2b77543a77ea0fd6a74e3e56bea6ef5c4ec0b5ec6cc735dcc98c1d27a31021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9e20c63185c3d3a4e69fe79e364b87048a0df6f54054a9019ebeaf831c00c7c 0.600000000000 1589473 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": 1110764, "vin": [ { "gen": { "height": 1110754 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9e20c63185c3d3a4e69fe79e364b87048a0df6f54054a9019ebeaf831c00c7c" } } ], "extra": [ 1, 82, 183, 210, 183, 117, 67, 167, 126, 160, 253, 106, 116, 227, 229, 107, 234, 110, 245, 196, 236, 11, 94, 198, 204, 115, 93, 204, 152, 193, 210, 122, 49, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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