Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ef9417dd680a823ebb1b5e39aa0f1435da45ab6df16104fc84b308d96967731

Tx prefix hash: 8112b32b95e91c1b6c1ad5b92161c0c2e8ac400b69408fbc605a06497fadd85b
Tx public key: 2601bcc4f61f085b80d5e53262d257f95f390faece9c0e1c52b87d937f6eeb40
Timestamp: 1729370636 Timestamp [UCT]: 2024-10-19 20:43:56 Age [y:d:h:m:s]: 00:179:20:32:54
Block: 1135240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128321 RingCT/type: yes/0
Extra: 012601bcc4f61f085b80d5e53262d257f95f390faece9c0e1c52b87d937f6eeb400211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2b8036cee880461e6f7e73f0ab70d7607b374de2ec5285e2bf64579de4314cf 0.600000000000 1618571 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": 1135250, "vin": [ { "gen": { "height": 1135240 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2b8036cee880461e6f7e73f0ab70d7607b374de2ec5285e2bf64579de4314cf" } } ], "extra": [ 1, 38, 1, 188, 196, 246, 31, 8, 91, 128, 213, 229, 50, 98, 210, 87, 249, 95, 57, 15, 174, 206, 156, 14, 28, 82, 184, 125, 147, 127, 110, 235, 64, 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