Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e53d3ba4ca9c8f1f66fde8ef167fc416e97c2ffab898a8ae21ed37ec0686268

Tx prefix hash: 8c6ecde9e23a134642c8aa1fe65f466197e2defa2bc9cdad7683ba99c035e5e3
Tx public key: 5eb7eddf02fecf084f1ffdbf5268055dacab2aa945f3e5619d568a6237a7f521
Timestamp: 1746179624 Timestamp [UCT]: 2025-05-02 09:53:44 Age [y:d:h:m:s]: 00:198:08:44:41
Block: 1274071 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139491 RingCT/type: yes/0
Extra: 015eb7eddf02fecf084f1ffdbf5268055dacab2aa945f3e5619d568a6237a7f52102110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9157d46580d56490c6d8edfb582ea93fb918fda35225e2df578b5f751311f917 0.600000000000 1761360 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": 1274081, "vin": [ { "gen": { "height": 1274071 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9157d46580d56490c6d8edfb582ea93fb918fda35225e2df578b5f751311f917" } } ], "extra": [ 1, 94, 183, 237, 223, 2, 254, 207, 8, 79, 31, 253, 191, 82, 104, 5, 93, 172, 171, 42, 169, 69, 243, 229, 97, 157, 86, 138, 98, 55, 167, 245, 33, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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