Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea67a1a2c0c0249518d675d0a4e97563567fbcce04d4f04f177979276752a95d

Tx prefix hash: d2d18bf738ad5b6f5f70349f5b2f9ad58c2b379d0b1ccd23e8d206aac7f680b2
Tx public key: 8b4d8049e8738589054d511d2dddba3055f2e28b1c28c924a01ba0b0710e937f
Timestamp: 1719322574 Timestamp [UCT]: 2024-06-25 13:36:14 Age [y:d:h:m:s]: 01:133:11:03:21
Block: 1051931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353919 RingCT/type: yes/0
Extra: 018b4d8049e8738589054d511d2dddba3055f2e28b1c28c924a01ba0b0710e937f0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a3aa30431a047b6c081694a644b6bcab1c1a0f661c0e260be620b3a3dfd1935 0.600000000000 1522252 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": 1051941, "vin": [ { "gen": { "height": 1051931 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a3aa30431a047b6c081694a644b6bcab1c1a0f661c0e260be620b3a3dfd1935" } } ], "extra": [ 1, 139, 77, 128, 73, 232, 115, 133, 137, 5, 77, 81, 29, 45, 221, 186, 48, 85, 242, 226, 139, 28, 40, 201, 36, 160, 27, 160, 176, 113, 14, 147, 127, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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