Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c6a292b23a51ef724173fc707da04edc976033e948e8cd90aa0124faad5b602

Tx prefix hash: ca249baade382c2312cbe154818bc89be102abcf8d7cc45c5f67ae98523dc0fd
Tx public key: 5a5d12d53b4fff918995f9fba1dd9587505109aebfbc22070c3b41c2e918b688
Timestamp: 1719903206 Timestamp [UCT]: 2024-07-02 06:53:26 Age [y:d:h:m:s]: 00:290:08:39:37
Block: 1056755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207482 RingCT/type: yes/0
Extra: 015a5d12d53b4fff918995f9fba1dd9587505109aebfbc22070c3b41c2e918b688021100000001ddd3db91000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f87dd69eaaef0b596525076c0ecd522d22bd4370135e50b1e68ed3402df8f70 0.600000000000 1527178 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": 1056765, "vin": [ { "gen": { "height": 1056755 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f87dd69eaaef0b596525076c0ecd522d22bd4370135e50b1e68ed3402df8f70" } } ], "extra": [ 1, 90, 93, 18, 213, 59, 79, 255, 145, 137, 149, 249, 251, 161, 221, 149, 135, 80, 81, 9, 174, 191, 188, 34, 7, 12, 59, 65, 194, 233, 24, 182, 136, 2, 17, 0, 0, 0, 1, 221, 211, 219, 145, 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