Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f9175fd7380bb106e5f53aeed4a56cb98d8db1d9111bf6be900d2f29252b992

Tx prefix hash: c0b40d9e590c126c53845facabedfad1ace1d50871f45da592258d62f2e8b65c
Tx public key: 8613caa24de9c2a99fc5e38859621f9724181bfb654dc07f97dddb97bd9cd238
Timestamp: 1729515481 Timestamp [UCT]: 2024-10-21 12:58:01 Age [y:d:h:m:s]: 00:188:05:52:14
Block: 1136407 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134357 RingCT/type: yes/0
Extra: 018613caa24de9c2a99fc5e38859621f9724181bfb654dc07f97dddb97bd9cd238021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e5552ffa55cb4964b3a2350d4d2b088a0286e7a32d8b8288de299a783dbfb97 0.600000000000 1619752 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": 1136417, "vin": [ { "gen": { "height": 1136407 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e5552ffa55cb4964b3a2350d4d2b088a0286e7a32d8b8288de299a783dbfb97" } } ], "extra": [ 1, 134, 19, 202, 162, 77, 233, 194, 169, 159, 197, 227, 136, 89, 98, 31, 151, 36, 24, 27, 251, 101, 77, 192, 127, 151, 221, 219, 151, 189, 156, 210, 56, 2, 17, 0, 0, 0, 1, 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