Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84839fd4493c8b2ef9a965936ad8254b0ddb5c40aac964a1e66de44db89986fd

Tx prefix hash: 7ce183df347f0eb3ff300d33add8dcc784425b9ef49aee09b44c24a7343370de
Tx public key: 8f90d12bbff985999b0cc0c137684a3597f1cb0b6c6593b37f46d5202393b48f
Timestamp: 1702325543 Timestamp [UCT]: 2023-12-11 20:12:23 Age [y:d:h:m:s]: 01:335:04:21:06
Block: 911027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498418 RingCT/type: yes/0
Extra: 018f90d12bbff985999b0cc0c137684a3597f1cb0b6c6593b37f46d5202393b48f02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7f1e6e3ddd988ed0e30e0108ce808cfa77d07a42cf46b58f5f92a798bb868b4 0.600000000000 1368202 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": 911037, "vin": [ { "gen": { "height": 911027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7f1e6e3ddd988ed0e30e0108ce808cfa77d07a42cf46b58f5f92a798bb868b4" } } ], "extra": [ 1, 143, 144, 209, 43, 191, 249, 133, 153, 155, 12, 192, 193, 55, 104, 74, 53, 151, 241, 203, 11, 108, 101, 147, 179, 127, 70, 213, 32, 35, 147, 180, 143, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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