Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f929c126b22125e532e0ca386fafa40455e9b05307d32461e514955de18c5af0

Tx prefix hash: 7fa95f3f59720ab8901c660bd285fd82011a7114cd60066cad40a47a8435bef6
Tx public key: a89afbe730d02b0ba8a23285025da28c1da26e6dc46bd1245b5b388e0aae3b5d
Timestamp: 1721935282 Timestamp [UCT]: 2024-07-25 19:21:22 Age [y:d:h:m:s]: 00:243:11:20:53
Block: 1073598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173907 RingCT/type: yes/0
Extra: 01a89afbe730d02b0ba8a23285025da28c1da26e6dc46bd1245b5b388e0aae3b5d021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb1ac16d87a0a4037ab48574d18c4e879945fd5e821b8db5aa5de6ed54e44946 0.600000000000 1546103 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": 1073608, "vin": [ { "gen": { "height": 1073598 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb1ac16d87a0a4037ab48574d18c4e879945fd5e821b8db5aa5de6ed54e44946" } } ], "extra": [ 1, 168, 154, 251, 231, 48, 208, 43, 11, 168, 162, 50, 133, 2, 93, 162, 140, 29, 162, 110, 109, 196, 107, 209, 36, 91, 91, 56, 142, 10, 174, 59, 93, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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