Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 745a63f94d74ddd0be6a751451789256a399fd905369986ce0f85d4ba5e0d9fd

Tx prefix hash: 22e4a6067f283131ad88cf32ed854c21d3d96f2e2bb28147ff2148e9864b7f3b
Tx public key: c8ef8016edde95ae8dd88ad339c7ba3b7d516603bac178a028814adc3c81b0f5
Timestamp: 1735716779 Timestamp [UCT]: 2025-01-01 07:32:59 Age [y:d:h:m:s]: 00:097:16:04:59
Block: 1187722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69587 RingCT/type: yes/0
Extra: 01c8ef8016edde95ae8dd88ad339c7ba3b7d516603bac178a028814adc3c81b0f502110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c57c63541141953229d1da7ea2b264331eaa482f6e8e612e341552d4a9252bd 0.600000000000 1674215 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": 1187732, "vin": [ { "gen": { "height": 1187722 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c57c63541141953229d1da7ea2b264331eaa482f6e8e612e341552d4a9252bd" } } ], "extra": [ 1, 200, 239, 128, 22, 237, 222, 149, 174, 141, 216, 138, 211, 57, 199, 186, 59, 125, 81, 102, 3, 186, 193, 120, 160, 40, 129, 74, 220, 60, 129, 176, 245, 2, 17, 0, 0, 0, 10, 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