Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2f40b3ebbb4a9062df4e2fd7109e1fc459587fb494332aad16f7bb0ac0a3584

Tx prefix hash: 9b06a740722b9fec57a2b1416a3365f2e796878d0f3a9f9aa786fb025321723c
Tx public key: fdc03300ebe781a3bdc0b7b702b362106e3e69806fe7a284a08ea90bef60c210
Timestamp: 1750261544 Timestamp [UCT]: 2025-06-18 15:45:44 Age [y:d:h:m:s]: 00:155:09:48:09
Block: 1307749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108867 RingCT/type: yes/0
Extra: 01fdc03300ebe781a3bdc0b7b702b362106e3e69806fe7a284a08ea90bef60c21002110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c75f26698969781becd1956d515d94529d72fd21ecbc2fb36b7fe81e60d1dd7 0.600000000000 1795360 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": 1307759, "vin": [ { "gen": { "height": 1307749 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c75f26698969781becd1956d515d94529d72fd21ecbc2fb36b7fe81e60d1dd7" } } ], "extra": [ 1, 253, 192, 51, 0, 235, 231, 129, 163, 189, 192, 183, 183, 2, 179, 98, 16, 110, 62, 105, 128, 111, 231, 162, 132, 160, 142, 169, 11, 239, 96, 194, 16, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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