Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 543b7fd88ed47d7e2d9bc543f52413de870c57da746c1a6553013ede543cf88a

Tx prefix hash: 6fba56b01c92d548b1e4ab28b57f746585d87ff7933d1c8bcfcdead3b08a956a
Tx public key: a4d569639d74c962f1dcf64ae87b9dd055fd7678d74c832156c9bc1786543cfe
Timestamp: 1750512444 Timestamp [UCT]: 2025-06-21 13:27:24 Age [y:d:h:m:s]: 00:152:14:37:13
Block: 1309776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106916 RingCT/type: yes/0
Extra: 01a4d569639d74c962f1dcf64ae87b9dd055fd7678d74c832156c9bc1786543cfe02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d956a26976f41c935d2e22ac2fe83303cd93b8e418495c8386cd0a72c51e9da3 0.600000000000 1797393 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": 1309786, "vin": [ { "gen": { "height": 1309776 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d956a26976f41c935d2e22ac2fe83303cd93b8e418495c8386cd0a72c51e9da3" } } ], "extra": [ 1, 164, 213, 105, 99, 157, 116, 201, 98, 241, 220, 246, 74, 232, 123, 157, 208, 85, 253, 118, 120, 215, 76, 131, 33, 86, 201, 188, 23, 134, 84, 60, 254, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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