Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb7c39acf60b06715170a62c7fe968bfcb093a89b935359c444ce43ac96dbd3e

Tx prefix hash: 2cc411d9f8cbccc74507b7f3731f07278fc07c751324989533a1551d714ab091
Tx public key: 4b048ae9b28d0363ceddcbabce6df2d5dd6407c4dde17c743d21dc0682fdbe5a
Timestamp: 1687106285 Timestamp [UCT]: 2023-06-18 16:38:05 Age [y:d:h:m:s]: 01:341:11:20:09
Block: 785110 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 505249 RingCT/type: yes/0
Extra: 014b048ae9b28d0363ceddcbabce6df2d5dd6407c4dde17c743d21dc0682fdbe5a0211000000044b8f5122000000000000000000

1 output(s) for total of 1.536755609000 dcy

stealth address amount amount idx
00: 00f55a7e2dc007e9bea0e72cdecddaa0d196e75c2cce5d4bc226b51dd5b3a1b0 1.536755609000 1235039 of 0

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": 785120, "vin": [ { "gen": { "height": 785110 } } ], "vout": [ { "amount": 1536755609, "target": { "key": "00f55a7e2dc007e9bea0e72cdecddaa0d196e75c2cce5d4bc226b51dd5b3a1b0" } } ], "extra": [ 1, 75, 4, 138, 233, 178, 141, 3, 99, 206, 221, 203, 171, 206, 109, 242, 213, 221, 100, 7, 196, 221, 225, 124, 116, 61, 33, 220, 6, 130, 253, 190, 90, 2, 17, 0, 0, 0, 4, 75, 143, 81, 34, 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