Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 600a4f72304bcaac5715f4a46bf99a5a8a78e65c48d69a70a66ac4e843b17f88

Tx prefix hash: 0ddc6ae461c7374c2fd52437a227fff45d1d590dd55756a2e743c7894d215fff
Tx public key: 63a9c78f11bdc455ac98729b0aaf452b57417dcd842e17e5c426ad20aa67f52d
Timestamp: 1710335818 Timestamp [UCT]: 2024-03-13 13:16:58 Age [y:d:h:m:s]: 00:301:15:45:38
Block: 977461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215909 RingCT/type: yes/0
Extra: 0163a9c78f11bdc455ac98729b0aaf452b57417dcd842e17e5c426ad20aa67f52d0211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 595e5b8bcb8d24373a22e917c07c5a9b487b9bcc374fc4823d6f35280f1f7eb8 0.600000000000 1437464 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": 977471, "vin": [ { "gen": { "height": 977461 } } ], "vout": [ { "amount": 600000000, "target": { "key": "595e5b8bcb8d24373a22e917c07c5a9b487b9bcc374fc4823d6f35280f1f7eb8" } } ], "extra": [ 1, 99, 169, 199, 143, 17, 189, 196, 85, 172, 152, 114, 155, 10, 175, 69, 43, 87, 65, 125, 205, 132, 46, 23, 229, 196, 38, 173, 32, 170, 103, 245, 45, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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