Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a98f06a7e9a49931c91bdbdc430cf78e5ca5009ffba7b462037add70b5e38d39

Tx prefix hash: ce13382a49cdb5365e7cfa6ea9e6ff441e0b78cddfc1ed08c98ea7f11b57dd70
Tx public key: aac457993e3ad97e9cbe0d6e00545c324b31f5e143a418341a4fd8e1cf935d0f
Timestamp: 1676242449 Timestamp [UCT]: 2023-02-12 22:54:09 Age [y:d:h:m:s]: 02:053:13:24:47
Block: 695677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 559865 RingCT/type: yes/0
Extra: 01aac457993e3ad97e9cbe0d6e00545c324b31f5e143a418341a4fd8e1cf935d0f0211000000065029cbac000000000000000000

1 output(s) for total of 3.040417540000 dcy

stealth address amount amount idx
00: a4be695abc7111b0e98aefc72681ce5c6f8f82eba2e2accf2985ca963597a144 3.040417540000 1138634 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": 695687, "vin": [ { "gen": { "height": 695677 } } ], "vout": [ { "amount": 3040417540, "target": { "key": "a4be695abc7111b0e98aefc72681ce5c6f8f82eba2e2accf2985ca963597a144" } } ], "extra": [ 1, 170, 196, 87, 153, 62, 58, 217, 126, 156, 190, 13, 110, 0, 84, 92, 50, 75, 49, 245, 225, 67, 164, 24, 52, 26, 79, 216, 225, 207, 147, 93, 15, 2, 17, 0, 0, 0, 6, 80, 41, 203, 172, 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