Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a15758d3b0a8e6778e7d28c8153b83ed14f1a1359a1e29c1315b6a3e2fb7243

Tx prefix hash: a6dfc0d1cf97557bf3889d92b4c1528a00edcbef76eb94279393c5b2bf5745e8
Tx public key: 444c18575b996aa75116d093781f8569a3d4c5eebf2960a4e09250ee582297d2
Timestamp: 1755160049 Timestamp [UCT]: 2025-08-14 08:27:29 Age [y:d:h:m:s]: 00:142:18:06:23
Block: 1346548 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101624 RingCT/type: yes/0
Extra: 01444c18575b996aa75116d093781f8569a3d4c5eebf2960a4e09250ee582297d20211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da13903b916b6f3098ccb383263a994e5840f0ec2bf1ddbfd8989e0def4ff9d0 0.600000000000 1834449 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": 1346558, "vin": [ { "gen": { "height": 1346548 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da13903b916b6f3098ccb383263a994e5840f0ec2bf1ddbfd8989e0def4ff9d0" } } ], "extra": [ 1, 68, 76, 24, 87, 91, 153, 106, 167, 81, 22, 208, 147, 120, 31, 133, 105, 163, 212, 197, 238, 191, 41, 96, 164, 224, 146, 80, 238, 88, 34, 151, 210, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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