Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a36499e3ecc8d8caf5cebf6847ac33cc07e680f48fddaf4a4bbe10c5cac5dd0

Tx prefix hash: fea83a37c44305e84b83a67b43f6f63acb819512787438adea9dcc1f909e50f1
Tx public key: b0719ec5b9562b70fa2eac2eeb8c954b3de6676cb2f47971a68a242e009635d4
Timestamp: 1685331380 Timestamp [UCT]: 2023-05-29 03:36:20 Age [y:d:h:m:s]: 01:180:03:18:34
Block: 770385 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390132 RingCT/type: yes/0
Extra: 01b0719ec5b9562b70fa2eac2eeb8c954b3de6676cb2f47971a68a242e009635d4021100000003e6d27f9c000000000000000000

1 output(s) for total of 1.719471042000 dcy

stealth address amount amount idx
00: 1ca1101ad06f6a355773d477c24ed41f7820087096aafa349804c253195e427f 1.719471042000 1219690 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": 770395, "vin": [ { "gen": { "height": 770385 } } ], "vout": [ { "amount": 1719471042, "target": { "key": "1ca1101ad06f6a355773d477c24ed41f7820087096aafa349804c253195e427f" } } ], "extra": [ 1, 176, 113, 158, 197, 185, 86, 43, 112, 250, 46, 172, 46, 235, 140, 149, 75, 61, 230, 103, 108, 178, 244, 121, 113, 166, 138, 36, 46, 0, 150, 53, 212, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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