Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebfc4a91136d98f848ea30e5e86f29276addfc9b919d4f6d7805b0cada701ef4

Tx prefix hash: bb799e21f240157f0a1d9cf455b904ac72c3cea109b5438a7be52b6e4907d5cd
Tx public key: 561741daff6a27fdbc915ec53711d7a29b12ab9e0950c5b4569abb9486b7ebfc
Timestamp: 1740287220 Timestamp [UCT]: 2025-02-23 05:07:00 Age [y:d:h:m:s]: 00:019:04:41:30
Block: 1225275 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13768 RingCT/type: yes/0
Extra: 01561741daff6a27fdbc915ec53711d7a29b12ab9e0950c5b4569abb9486b7ebfc0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d4c0673c123454fc04a0acb6b93be559f0257bf2e9e0e4040a9bd4e5392f226 0.600000000000 1712140 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": 1225285, "vin": [ { "gen": { "height": 1225275 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d4c0673c123454fc04a0acb6b93be559f0257bf2e9e0e4040a9bd4e5392f226" } } ], "extra": [ 1, 86, 23, 65, 218, 255, 106, 39, 253, 188, 145, 94, 197, 55, 17, 215, 162, 155, 18, 171, 158, 9, 80, 197, 180, 86, 154, 187, 148, 134, 183, 235, 252, 2, 17, 0, 0, 0, 2, 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