Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e7a845c0b17a7bd8af1dc218074dc08dfeb9fc62464978605072890cc6c4659

Tx prefix hash: 6bc5b237ba56e8095fe0f1daf3a1264464bddc15c57a7f3b28f2c736b1bb14a6
Tx public key: 5ecd035329e65f497608e29e93839c3a6bbae945a1dd009db9b6b859a15945b2
Timestamp: 1761570422 Timestamp [UCT]: 2025-10-27 13:07:02 Age [y:d:h:m:s]: 00:017:00:35:17
Block: 1399084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12179 RingCT/type: yes/0
Extra: 015ecd035329e65f497608e29e93839c3a6bbae945a1dd009db9b6b859a15945b2021100000004df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d776218d708ceda5a0c8d6f1e1cc21a074799e499439b739083ca37a22a2dfa 0.600000000000 1887387 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": 1399094, "vin": [ { "gen": { "height": 1399084 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d776218d708ceda5a0c8d6f1e1cc21a074799e499439b739083ca37a22a2dfa" } } ], "extra": [ 1, 94, 205, 3, 83, 41, 230, 95, 73, 118, 8, 226, 158, 147, 131, 156, 58, 107, 186, 233, 69, 161, 221, 0, 157, 185, 182, 184, 89, 161, 89, 69, 178, 2, 17, 0, 0, 0, 4, 223, 90, 36, 122, 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