Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 824b39a2dffe15ee8c83bfae11a958a6f5683bb33524bc16b243f40b1df086d9

Tx prefix hash: d766d6b874621804c9f4d14352e7eea6a68852d3210652c2969ed157c7bf6918
Tx public key: 5f51e2dab5d89c96a6c881b4b54667c068c1de91a694b2deed2fe4073eaabcf6
Timestamp: 1729067249 Timestamp [UCT]: 2024-10-16 08:27:29 Age [y:d:h:m:s]: 00:000:07:51:27
Block: 1132735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232 RingCT/type: yes/0
Extra: 015f51e2dab5d89c96a6c881b4b54667c068c1de91a694b2deed2fe4073eaabcf6021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec3145b136c34032b7121ab8312ae1b2d6cee3819624024326dc473cb3480631 0.600000000000 1615718 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": 1132745, "vin": [ { "gen": { "height": 1132735 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec3145b136c34032b7121ab8312ae1b2d6cee3819624024326dc473cb3480631" } } ], "extra": [ 1, 95, 81, 226, 218, 181, 216, 156, 150, 166, 200, 129, 180, 181, 70, 103, 192, 104, 193, 222, 145, 166, 148, 178, 222, 237, 47, 228, 7, 62, 170, 188, 246, 2, 17, 0, 0, 0, 5, 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