Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60bca671e864c43cb6872bee8a0bbd18b9bf4cc6f8084a69807d433f83a9f405

Tx prefix hash: ef8d550862d5526dc09f947c5cc9c5db127b13b840c721b8ae03a5393cc52d84
Tx public key: f4ef9be6da10b577822136842088e8f88975e353be301dae98efd79d79301f26
Timestamp: 1701611766 Timestamp [UCT]: 2023-12-03 13:56:06 Age [y:d:h:m:s]: 01:144:09:30:44
Block: 905099 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364352 RingCT/type: yes/0
Extra: 01f4ef9be6da10b577822136842088e8f88975e353be301dae98efd79d79301f26021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.615221160000 dcy

stealth address amount amount idx
00: 92e8b3c79a302c7791630d410c0109d2af84f6e4e8851d43b17d9721bfca07fd 0.615221160000 1361970 of 0

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": 905109, "vin": [ { "gen": { "height": 905099 } } ], "vout": [ { "amount": 615221160, "target": { "key": "92e8b3c79a302c7791630d410c0109d2af84f6e4e8851d43b17d9721bfca07fd" } } ], "extra": [ 1, 244, 239, 155, 230, 218, 16, 181, 119, 130, 33, 54, 132, 32, 136, 232, 248, 137, 117, 227, 83, 190, 48, 29, 174, 152, 239, 215, 157, 121, 48, 31, 38, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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