Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75b45da75ce52e30a4d14bbef35480b85e185358c3c03984d13eba4b31fcd5e5

Tx prefix hash: 8913a4dc885c9cf2d8aac25c11906c7d2ef1ec9fb8558f57f3ea53832f5bc832
Tx public key: e3fcd2cf0634d8ebf618039e4380d5c0555c356c98452b6c844a2f2fab94a7b4
Timestamp: 1728236242 Timestamp [UCT]: 2024-10-06 17:37:22 Age [y:d:h:m:s]: 01:045:10:23:18
Block: 1125840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290850 RingCT/type: yes/0
Extra: 01e3fcd2cf0634d8ebf618039e4380d5c0555c356c98452b6c844a2f2fab94a7b402110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ddc319f80bff0eb048f86b205a84e46f9d33aff6c84deffb3cf7f7f47c0f16d8 0.600000000000 1608593 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": 1125850, "vin": [ { "gen": { "height": 1125840 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ddc319f80bff0eb048f86b205a84e46f9d33aff6c84deffb3cf7f7f47c0f16d8" } } ], "extra": [ 1, 227, 252, 210, 207, 6, 52, 216, 235, 246, 24, 3, 158, 67, 128, 213, 192, 85, 92, 53, 108, 152, 69, 43, 108, 132, 74, 47, 47, 171, 148, 167, 180, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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