Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b110e1a362a68e775ca3a745ef6aeb8cb5270e4b79774a853f3eca375a7c6fe

Tx prefix hash: 708028bd01eac2fc70d86e3a3eb5c33bc16dd378a0862494edc8f4b83ed1859d
Tx public key: 7a2c32ef80a2a9b0cf13183cf7620cd9da0aba9ff895bff3f7cfebfbb54e4e2a
Timestamp: 1746227953 Timestamp [UCT]: 2025-05-02 23:19:13 Age [y:d:h:m:s]: 00:203:00:11:00
Block: 1274477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142803 RingCT/type: yes/0
Extra: 017a2c32ef80a2a9b0cf13183cf7620cd9da0aba9ff895bff3f7cfebfbb54e4e2a02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df16271b80f978ddd79abc2174140002d26d8795860506d4f4ef41b2cc3f63d3 0.600000000000 1761772 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": 1274487, "vin": [ { "gen": { "height": 1274477 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df16271b80f978ddd79abc2174140002d26d8795860506d4f4ef41b2cc3f63d3" } } ], "extra": [ 1, 122, 44, 50, 239, 128, 162, 169, 176, 207, 19, 24, 60, 247, 98, 12, 217, 218, 10, 186, 159, 248, 149, 191, 243, 247, 207, 235, 251, 181, 78, 78, 42, 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