Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79d85eb3fb1d918b893703c3343778fe2670025358a0395e2d4d11a3a9f320f0

Tx prefix hash: e1a55a384717610aab8f13b1eb9e0d7d75bd8fe784b13397d06917d9e620fa68
Tx public key: 52213a41dcec68a9323ca88e0ce611b1a65df36a94353707c434a2f4a460917b
Timestamp: 1716291115 Timestamp [UCT]: 2024-05-21 11:31:55 Age [y:d:h:m:s]: 01:177:01:46:23
Block: 1026821 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385149 RingCT/type: yes/0
Extra: 0152213a41dcec68a9323ca88e0ce611b1a65df36a94353707c434a2f4a460917b0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f8b06943ce8c2bfde54afb3fdd02e7108fc5bc6019dc2e603f2984694ca9fae 0.600000000000 1494108 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": 1026831, "vin": [ { "gen": { "height": 1026821 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f8b06943ce8c2bfde54afb3fdd02e7108fc5bc6019dc2e603f2984694ca9fae" } } ], "extra": [ 1, 82, 33, 58, 65, 220, 236, 104, 169, 50, 60, 168, 142, 12, 230, 17, 177, 166, 93, 243, 106, 148, 53, 55, 7, 196, 52, 162, 244, 164, 96, 145, 123, 2, 17, 0, 0, 0, 5, 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