Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ab417131edf183415d92bddb8072fd735212d1e2d3d0bbc96bc02977e55ff28

Tx prefix hash: 4a59456fc17615e96e3855ecae3b52716ce0c7aae11b04dc4e43d6b073e14fdb
Tx public key: e1a8d97a7dab399d31a61ba1cb51cbfeac687bfa1184ac2986e4f1751f5544bd
Timestamp: 1738651895 Timestamp [UCT]: 2025-02-04 06:51:35 Age [y:d:h:m:s]: 00:290:17:30:25
Block: 1211753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205552 RingCT/type: yes/0
Extra: 01e1a8d97a7dab399d31a61ba1cb51cbfeac687bfa1184ac2986e4f1751f5544bd021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05546505b6336fa114dfb2b5980b37db6156494f0eef9fbf42bffd000cc3a5c3 0.600000000000 1698516 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": 1211763, "vin": [ { "gen": { "height": 1211753 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05546505b6336fa114dfb2b5980b37db6156494f0eef9fbf42bffd000cc3a5c3" } } ], "extra": [ 1, 225, 168, 217, 122, 125, 171, 57, 157, 49, 166, 27, 161, 203, 81, 203, 254, 172, 104, 123, 250, 17, 132, 172, 41, 134, 228, 241, 117, 31, 85, 68, 189, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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