Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8fe97e3e8bbe1ce0594ba13eae90034b2a3f4f91ee36060f3b318302c6851bd6

Tx prefix hash: ab051eab4b11121355ea5c415656e29c9359b80e92423314be3ba42792ab50f4
Tx public key: b0549d978ff582d2f1b5dcb590327951d22cfb0e2f73fbfe4cd01f1c12a79ffb
Timestamp: 1698391109 Timestamp [UCT]: 2023-10-27 07:18:29 Age [y:d:h:m:s]: 01:086:09:46:26
Block: 878622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322926 RingCT/type: yes/0
Extra: 01b0549d978ff582d2f1b5dcb590327951d22cfb0e2f73fbfe4cd01f1c12a79ffb0211000000024b8f5122000000000000000000

1 output(s) for total of 0.752940391000 dcy

stealth address amount amount idx
00: 239ab489a0fcb5c12d8407a6c51012fbe1ceb3de63ecba323c45f1be92e9b5af 0.752940391000 1334084 of 0

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": 878632, "vin": [ { "gen": { "height": 878622 } } ], "vout": [ { "amount": 752940391, "target": { "key": "239ab489a0fcb5c12d8407a6c51012fbe1ceb3de63ecba323c45f1be92e9b5af" } } ], "extra": [ 1, 176, 84, 157, 151, 143, 245, 130, 210, 241, 181, 220, 181, 144, 50, 121, 81, 210, 44, 251, 14, 47, 115, 251, 254, 76, 208, 31, 28, 18, 167, 159, 251, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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