Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc40042fe0a73d8e9ecc2d50ce490ef6dcfb6dd29c3b6d67cbcb770d573794c0

Tx prefix hash: 4140ac1450823fe67a4b4624eee54640b1fb3823279c4114aa4c3f049fc91b8a
Tx public key: 92b505be4e9e0cdb04c0f00b874e318510258aaee00742ab4d789ed7cd31902c
Timestamp: 1700836754 Timestamp [UCT]: 2023-11-24 14:39:14 Age [y:d:h:m:s]: 01:180:09:35:33
Block: 898678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390141 RingCT/type: yes/0
Extra: 0192b505be4e9e0cdb04c0f00b874e318510258aaee00742ab4d789ed7cd31902c021100000003faf35c9c000000000000000000

1 output(s) for total of 0.646110371000 dcy

stealth address amount amount idx
00: 7f45d9a804ff7cbc220130198d6082fabe481828c6cff1faabdf14284c5936ab 0.646110371000 1355107 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": 898688, "vin": [ { "gen": { "height": 898678 } } ], "vout": [ { "amount": 646110371, "target": { "key": "7f45d9a804ff7cbc220130198d6082fabe481828c6cff1faabdf14284c5936ab" } } ], "extra": [ 1, 146, 181, 5, 190, 78, 158, 12, 219, 4, 192, 240, 11, 135, 78, 49, 133, 16, 37, 138, 174, 224, 7, 66, 171, 77, 120, 158, 215, 205, 49, 144, 44, 2, 17, 0, 0, 0, 3, 250, 243, 92, 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