Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21a25524755827aaeb91c2f64fe1171de8615af1c1f9a41ea902424915dc6905

Tx prefix hash: 21b46b6e2ae909eb9c154edb361ea0fa699007b75123512ff74724d6131b4b3f
Tx public key: 7597ae48e0cafd2746f6cde6c5988650a59aaae0154f8b6bb2ea6c689cf747b0
Timestamp: 1713060780 Timestamp [UCT]: 2024-04-14 02:13:00 Age [y:d:h:m:s]: 00:361:20:53:04
Block: 1000009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258721 RingCT/type: yes/0
Extra: 017597ae48e0cafd2746f6cde6c5988650a59aaae0154f8b6bb2ea6c689cf747b002110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c39e867973d5890633aa11b3ee1f1fe1cdb0a7bc7ac739e23b6ce6153129b033 0.600000000000 1460497 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": 1000019, "vin": [ { "gen": { "height": 1000009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c39e867973d5890633aa11b3ee1f1fe1cdb0a7bc7ac739e23b6ce6153129b033" } } ], "extra": [ 1, 117, 151, 174, 72, 224, 202, 253, 39, 70, 246, 205, 230, 197, 152, 134, 80, 165, 154, 170, 224, 21, 79, 139, 107, 178, 234, 108, 104, 156, 247, 71, 176, 2, 17, 0, 0, 0, 10, 89, 218, 211, 245, 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