Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 192afa8a789aa3c2e4234118a6574ecdda69f8bc1c00aea6e0d78ce4c432549a

Tx prefix hash: e10d3ac53b239e94ea9bb6f3c51a4f485552edb781f01415b56c262fc219b54a
Tx public key: 36a31c36e193fa7bc5febf884a63a44a5a329e82a3bb90f95fa00ac1341eb3b0
Timestamp: 1720387190 Timestamp [UCT]: 2024-07-07 21:19:50 Age [y:d:h:m:s]: 00:317:23:54:45
Block: 1060766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227255 RingCT/type: yes/0
Extra: 0136a31c36e193fa7bc5febf884a63a44a5a329e82a3bb90f95fa00ac1341eb3b0021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe7b9337fc93a699522b90900689e984a1395404f2efe081eec539d34d9f08c0 0.600000000000 1531251 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": 1060776, "vin": [ { "gen": { "height": 1060766 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe7b9337fc93a699522b90900689e984a1395404f2efe081eec539d34d9f08c0" } } ], "extra": [ 1, 54, 163, 28, 54, 225, 147, 250, 123, 197, 254, 191, 136, 74, 99, 164, 74, 90, 50, 158, 130, 163, 187, 144, 249, 95, 160, 10, 193, 52, 30, 179, 176, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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