Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7da015b6c039af781ce826c976fb316535dc91d42306f1feea59086e933d583c

Tx prefix hash: 39cf493fe38f87b14ba03395a44349d6a6f89e3166dbf4fea2ccb688c26fc31e
Tx public key: b98314b1083173e448fa4b1c5bdc2441dd0702c210263de9749417bdc28a972e
Timestamp: 1725308486 Timestamp [UCT]: 2024-09-02 20:21:26 Age [y:d:h:m:s]: 00:288:06:13:31
Block: 1101565 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205791 RingCT/type: yes/0
Extra: 01b98314b1083173e448fa4b1c5bdc2441dd0702c210263de9749417bdc28a972e021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7500c88c622a411f93f4a91570ec41874d16a0e8f09ec0fb7abccb83df83fad 0.600000000000 1577664 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": 1101575, "vin": [ { "gen": { "height": 1101565 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7500c88c622a411f93f4a91570ec41874d16a0e8f09ec0fb7abccb83df83fad" } } ], "extra": [ 1, 185, 131, 20, 177, 8, 49, 115, 228, 72, 250, 75, 28, 91, 220, 36, 65, 221, 7, 2, 194, 16, 38, 61, 233, 116, 148, 23, 189, 194, 138, 151, 46, 2, 17, 0, 0, 0, 6, 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