Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ca9fd050b7ddc9502ec90519ff4b1f7a36c84f8c444a81cd97b38349c708c9a

Tx prefix hash: 9cbb412376e81549de63ac8bbd8140f6399e247bd2086f34eb94a802e7e73e81
Tx public key: fc9adbc01a49674ed2d60f7e29b23979637616daa32e1e68ba49f9f0c58bc168
Timestamp: 1677816946 Timestamp [UCT]: 2023-03-03 04:15:46 Age [y:d:h:m:s]: 02:038:00:04:34
Block: 708722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 548729 RingCT/type: yes/0
Extra: 01fc9adbc01a49674ed2d60f7e29b23979637616daa32e1e68ba49f9f0c58bc1680211000000015029cbac000000000000000000

1 output(s) for total of 2.752388344000 dcy

stealth address amount amount idx
00: f975ed78ee0c6ce0d6efeea5946392cec12fc1d01e4371d4df6ce2b24b11326d 2.752388344000 1152633 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": 708732, "vin": [ { "gen": { "height": 708722 } } ], "vout": [ { "amount": 2752388344, "target": { "key": "f975ed78ee0c6ce0d6efeea5946392cec12fc1d01e4371d4df6ce2b24b11326d" } } ], "extra": [ 1, 252, 154, 219, 192, 26, 73, 103, 78, 210, 214, 15, 126, 41, 178, 57, 121, 99, 118, 22, 218, 163, 46, 30, 104, 186, 73, 249, 240, 197, 139, 193, 104, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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