Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6450b5deb727ce27646208cca1934c69dff9e46dbdce42de1e33a4bce83cc1a

Tx prefix hash: 82131ffed7ae4e6ab2a59ff0d6a426c3ba5c4e40a7e875ced58679858bc0a9e2
Tx public key: 852c79cc903e9c080b29890852f71c4dc42928e9b7640806ee29c43db4422b08
Timestamp: 1699897064 Timestamp [UCT]: 2023-11-13 17:37:44 Age [y:d:h:m:s]: 01:182:08:44:35
Block: 890895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391543 RingCT/type: yes/0
Extra: 01852c79cc903e9c080b29890852f71c4dc42928e9b7640806ee29c43db4422b0802110000000133af99f4000000000000000000

1 output(s) for total of 0.685638243000 dcy

stealth address amount amount idx
00: a15e2db63181e7598d42f575571609014cd5c916c8149b6d466d0ed59ce69a88 0.685638243000 1346926 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": 890905, "vin": [ { "gen": { "height": 890895 } } ], "vout": [ { "amount": 685638243, "target": { "key": "a15e2db63181e7598d42f575571609014cd5c916c8149b6d466d0ed59ce69a88" } } ], "extra": [ 1, 133, 44, 121, 204, 144, 62, 156, 8, 11, 41, 137, 8, 82, 247, 28, 77, 196, 41, 40, 233, 183, 100, 8, 6, 238, 41, 196, 61, 180, 66, 43, 8, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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