Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61579a0b9ce99a0a612e48dba5003f17176586acdc7edb4f834da8098c26f4e8

Tx prefix hash: 4e911437372954c1ceeebbcc4aa1fec7d009b59b554f3696a65038ac33ab149e
Tx public key: a39982361577c8b5c01b65be100c4fa23ce53da8b5d645c1f4d750a991a8155d
Timestamp: 1722699010 Timestamp [UCT]: 2024-08-03 15:30:10 Age [y:d:h:m:s]: 01:121:06:11:37
Block: 1079929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345182 RingCT/type: yes/0
Extra: 01a39982361577c8b5c01b65be100c4fa23ce53da8b5d645c1f4d750a991a8155d02110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8aa7dcb4cae780595e12f4b32a7b3d8dc136b15ad6363b4cfea1c999d312524f 0.600000000000 1553090 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": 1079939, "vin": [ { "gen": { "height": 1079929 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8aa7dcb4cae780595e12f4b32a7b3d8dc136b15ad6363b4cfea1c999d312524f" } } ], "extra": [ 1, 163, 153, 130, 54, 21, 119, 200, 181, 192, 27, 101, 190, 16, 12, 79, 162, 60, 229, 61, 168, 181, 214, 69, 193, 244, 215, 80, 169, 145, 168, 21, 93, 2, 17, 0, 0, 0, 12, 145, 225, 60, 4, 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