Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31e292c3dfebc4ce2aeeab501ca63a3f9a455c87db4475fba62bb9cef45bd66a

Tx prefix hash: 0fa1ac4df6a3ef88ce68eedbddb3341e268ef0d052c385bd41d98d17b0444e2c
Tx public key: 3badc6b941fb002db34264997b6ce8d4c076eff0d61aae1978740f53ea1b41db
Timestamp: 1734730361 Timestamp [UCT]: 2024-12-20 21:32:41 Age [y:d:h:m:s]: 00:019:06:02:12
Block: 1179587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13739 RingCT/type: yes/0
Extra: 013badc6b941fb002db34264997b6ce8d4c076eff0d61aae1978740f53ea1b41db021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b25b74d3e95bfb8f863b954a5c71d410deffb5dbd97bb38828b5de04f1ce090 0.600000000000 1665984 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": 1179597, "vin": [ { "gen": { "height": 1179587 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b25b74d3e95bfb8f863b954a5c71d410deffb5dbd97bb38828b5de04f1ce090" } } ], "extra": [ 1, 59, 173, 198, 185, 65, 251, 0, 45, 179, 66, 100, 153, 123, 108, 232, 212, 192, 118, 239, 240, 214, 26, 174, 25, 120, 116, 15, 83, 234, 27, 65, 219, 2, 17, 0, 0, 0, 6, 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