Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f30e2ae67f9e03fff85087d0beb6ae5c5c2ad4166c819fec932c446e596b923

Tx prefix hash: 0187efcae3cd4e78ec36d9b98db4d68f7a1f09dcc1bcbed26187920b0a5d6d0b
Tx public key: eb6e01faf2d210f4f7dab651fd8b4de8429bf2b07acab26fcd7f55287b595108
Timestamp: 1736439859 Timestamp [UCT]: 2025-01-09 16:24:19 Age [y:d:h:m:s]: 00:070:05:35:05
Block: 1193715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49981 RingCT/type: yes/0
Extra: 01eb6e01faf2d210f4f7dab651fd8b4de8429bf2b07acab26fcd7f55287b5951080211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8d5fea97a458dbc1a2c9f4ea39ce68e9596cdc9a8b82c135ab201d3a4ca61b6 0.600000000000 1680280 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": 1193725, "vin": [ { "gen": { "height": 1193715 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8d5fea97a458dbc1a2c9f4ea39ce68e9596cdc9a8b82c135ab201d3a4ca61b6" } } ], "extra": [ 1, 235, 110, 1, 250, 242, 210, 16, 244, 247, 218, 182, 81, 253, 139, 77, 232, 66, 155, 242, 176, 122, 202, 178, 111, 205, 127, 85, 40, 123, 89, 81, 8, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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