Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6b8dba5b682f8043ddf74f2e35836ac8b6d145cb8cb249b094be34a200f12c1

Tx prefix hash: 0861517a2d8cd9d72214521ed5b3f91f0c8367549126f53de8fa1cef5711195c
Tx public key: 496b8f0a1dfdf982a70e4e5743cacea81d52cd4eda7f405b5a0cb55e339ada99
Timestamp: 1639132740 Timestamp [UCT]: 2021-12-10 10:39:00 Age [y:d:h:m:s]: 03:028:02:38:13
Block: 392431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 799056 RingCT/type: yes/0
Extra: 01496b8f0a1dfdf982a70e4e5743cacea81d52cd4eda7f405b5a0cb55e339ada99021100000002b494d89c000000000000000000

1 output(s) for total of 30.740685915000 dcy

stealth address amount amount idx
00: f0f9d5f84cbd09d912bbe3fc163191f12aa6d1e1f4afd7bbe051fa893a917251 30.740685915000 789300 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": 392441, "vin": [ { "gen": { "height": 392431 } } ], "vout": [ { "amount": 30740685915, "target": { "key": "f0f9d5f84cbd09d912bbe3fc163191f12aa6d1e1f4afd7bbe051fa893a917251" } } ], "extra": [ 1, 73, 107, 143, 10, 29, 253, 249, 130, 167, 14, 78, 87, 67, 202, 206, 168, 29, 82, 205, 78, 218, 127, 64, 91, 90, 12, 181, 94, 51, 154, 218, 153, 2, 17, 0, 0, 0, 2, 180, 148, 216, 156, 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