Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc936e261e2540486d6f8fec1ae59db9a11b8db650ab3c0f3beee6214e304e1e

Tx prefix hash: 50bdfa0f77918e3dde863d78327a1ccd1362b5532c728f45e40dbbc9e33a954e
Tx public key: 6b2f9c38da4b77c2e4472c288b1739db4d2417a255b6d9cec867a54a3b1e9181
Timestamp: 1638298468 Timestamp [UCT]: 2021-11-30 18:54:28 Age [y:d:h:m:s]: 03:161:22:48:39
Block: 385556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 894474 RingCT/type: yes/0
Extra: 016b2f9c38da4b77c2e4472c288b1739db4d2417a255b6d9cec867a54a3b1e9181021100000010e9564d6f000000000000000000

1 output(s) for total of 32.396141908000 dcy

stealth address amount amount idx
00: cc79eaf357bde6e690106cb9f22240a8012c0817e0ffd7b8990e7cbed0e9a89d 32.396141908000 778031 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": 385566, "vin": [ { "gen": { "height": 385556 } } ], "vout": [ { "amount": 32396141908, "target": { "key": "cc79eaf357bde6e690106cb9f22240a8012c0817e0ffd7b8990e7cbed0e9a89d" } } ], "extra": [ 1, 107, 47, 156, 56, 218, 75, 119, 194, 228, 71, 44, 40, 139, 23, 57, 219, 77, 36, 23, 162, 85, 182, 217, 206, 200, 103, 165, 74, 59, 30, 145, 129, 2, 17, 0, 0, 0, 16, 233, 86, 77, 111, 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