Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: feeec357a79c1f93c816ec814a983dd1b7d0b359c5049c76324c11414878b0cb

Tx prefix hash: 5dbcd7d7dae8820a7f75f0e395c331b948e4882c0a49485e72cdecc33ac1de58
Tx public key: 7437d661fad72b8f39ac6409cbe00b6e85365802d6ebc529dd4e20d9b58e1530
Timestamp: 1718477746 Timestamp [UCT]: 2024-06-15 18:55:46 Age [y:d:h:m:s]: 00:162:14:55:01
Block: 1044950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116375 RingCT/type: yes/0
Extra: 017437d661fad72b8f39ac6409cbe00b6e85365802d6ebc529dd4e20d9b58e1530021100000002befa2d88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 272adf817ca2adf643a3a75e6e20a3794b57bf4fc3b23ffa4cfb0f6155697943 0.600000000000 1514395 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": 1044960, "vin": [ { "gen": { "height": 1044950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "272adf817ca2adf643a3a75e6e20a3794b57bf4fc3b23ffa4cfb0f6155697943" } } ], "extra": [ 1, 116, 55, 214, 97, 250, 215, 43, 143, 57, 172, 100, 9, 203, 224, 11, 110, 133, 54, 88, 2, 214, 235, 197, 41, 221, 78, 32, 217, 181, 142, 21, 48, 2, 17, 0, 0, 0, 2, 190, 250, 45, 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