Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6f8a105ca5961fbffc0c5916228fa29a7a77a3735290de49b8cd0c911ee8563

Tx prefix hash: a7c05aa72d0cdc2f1aaa81ac419a20a8a33bd23d655459a0d3e7adf3bea69dee
Tx public key: 853836fd812d0945ad6cce4d50e5182939280e066a3a8d68aa388754e3ee4c1b
Timestamp: 1577799675 Timestamp [UCT]: 2019-12-31 13:41:15 Age [y:d:h:m:s]: 04:306:09:00:57
Block: 35808 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1107999 RingCT/type: yes/0
Extra: 01853836fd812d0945ad6cce4d50e5182939280e066a3a8d68aa388754e3ee4c1b021100000009d81c26c0000000000000000000

1 output(s) for total of 467.040008091000 dcy

stealth address amount amount idx
00: b76b9e6a48c5d6f1ec093d18aa1fbdb7ffd7937788862c73e1a8c178cf17f9ac 467.040008091000 60446 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": 35818, "vin": [ { "gen": { "height": 35808 } } ], "vout": [ { "amount": 467040008091, "target": { "key": "b76b9e6a48c5d6f1ec093d18aa1fbdb7ffd7937788862c73e1a8c178cf17f9ac" } } ], "extra": [ 1, 133, 56, 54, 253, 129, 45, 9, 69, 173, 108, 206, 77, 80, 229, 24, 41, 57, 40, 14, 6, 106, 58, 141, 104, 170, 56, 135, 84, 227, 238, 76, 27, 2, 17, 0, 0, 0, 9, 216, 28, 38, 192, 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