Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5222601f49948b11d75777b3fd30622ec06202cb227bf2c1da777fefc797ae8

Tx prefix hash: 3c4b2f47b2ef90266edfd8d1f2eea6ff8674fb30118ef3b7d2f0739d2ff3ffe1
Tx public key: ddcaab5148990e575c8acc429f197ef0df98569b007556c622ec1b97e697760f
Timestamp: 1713730573 Timestamp [UCT]: 2024-04-21 20:16:13 Age [y:d:h:m:s]: 01:198:01:53:31
Block: 1005568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 400202 RingCT/type: yes/0
Extra: 01ddcaab5148990e575c8acc429f197ef0df98569b007556c622ec1b97e697760f0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 953ccc2a87d0ac269d3afc610ecfea924b0d0f9d2dd3b1ed6d93d98bc01b4d30 0.600000000000 1466302 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": 1005578, "vin": [ { "gen": { "height": 1005568 } } ], "vout": [ { "amount": 600000000, "target": { "key": "953ccc2a87d0ac269d3afc610ecfea924b0d0f9d2dd3b1ed6d93d98bc01b4d30" } } ], "extra": [ 1, 221, 202, 171, 81, 72, 153, 14, 87, 92, 138, 204, 66, 159, 25, 126, 240, 223, 152, 86, 155, 0, 117, 86, 198, 34, 236, 27, 151, 230, 151, 118, 15, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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