Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba1db90d043703b88965f0e5438a6e87d5ba4611dff9c1b36aed32fb81503f97

Tx prefix hash: e82b9438163e585fff8cba33e8c2488799bd1d03ede5fe324b4b0631f02b0c57
Tx public key: 5b26403529f42704422fc43c7a180c93fd5bffc5bbe119f8fb6bae2a233600e5
Timestamp: 1717351679 Timestamp [UCT]: 2024-06-02 18:07:59 Age [y:d:h:m:s]: 00:305:01:55:24
Block: 1035610 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218014 RingCT/type: yes/0
Extra: 015b26403529f42704422fc43c7a180c93fd5bffc5bbe119f8fb6bae2a233600e502110000000341ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2003964672e31a0f3f4bd23cc8016450a4ffe85a61ddfbf4ba4c6085d912efe8 0.600000000000 1504131 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": 1035620, "vin": [ { "gen": { "height": 1035610 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2003964672e31a0f3f4bd23cc8016450a4ffe85a61ddfbf4ba4c6085d912efe8" } } ], "extra": [ 1, 91, 38, 64, 53, 41, 244, 39, 4, 66, 47, 196, 60, 122, 24, 12, 147, 253, 91, 255, 197, 187, 225, 25, 248, 251, 107, 174, 42, 35, 54, 0, 229, 2, 17, 0, 0, 0, 3, 65, 238, 28, 155, 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